Skip to content

Conversation

@AntonLydike
Copy link
Contributor

This is an attempt at fixing #277. I am not sure if such a breaking change would be justified though. Looking at the code, I definitely get the feeling, that it's supposed to return a NodeSet.

This probably has to wait for the next minor or even major release for that reason...

The documentation states, that a call to match() should return a
NodeSet. This change will however break existing code which expects
match() to return a Traversal.
This change was added to allow some backwards compatibility when working
with RelationshipManager.match(), which now returns a NodeSet as
was originally described in the documentation.
@aanastasiou
Copy link
Collaborator

@AntonLydike This looks like a good candidate to incorporate in the next round of changes. Is there any reason not to?

@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell B 7 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

idea Catch issues before they fail your Quality Gate with our IDE extension sonarlint SonarLint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants